Skip to content

Lock the setuptools build backend with hashes - #21

Merged
Abbasi26 merged 1 commit into
mainfrom
security/lock-build-deps
Nov 18, 2026
Merged

Abbasi26 merged 1 commit into
mainfrom
security/lock-build-deps

Conversation

@Abbasi26

Copy link
Copy Markdown
Owner

Follow-up from the dependency-pinning review. Draft, not for merge without Wasaf's OK.

  • requirements-ci.in / requirements-ci.txt: add setuptools==84.2.1 (the build backend from [build-system]), hash-locked.
  • CI: pip install --no-deps --no-build-isolation -e ., so the editable build uses the locked setuptools instead of downloading one without a hash.
  • action.yml: installs runtime dependencies from the new hash-pinned requirements-action.txt (--require-hashes, compiled with uv from requirements-action.in: cryptography, PyYAML, setuptools), then CertClock with --no-deps --no-build-isolation. The action path is passed through an env variable. Dependabot (uv ecosystem, directory /) picks up the new .in/.txt pair by name.

Local: full pytest suite passes with the locked set on Python 3.13; zizmor clean.

@Abbasi26
Abbasi26 marked this pull request as ready for review November 18, 2026 07:58
@Abbasi26
Abbasi26 merged commit 107ac56 into main Nov 18, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant